Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue 1063: change default guicursor behavior #1067

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

jgehrig
Copy link
Collaborator

@jgehrig jgehrig commented May 1, 2023

Issue #1063: can't disable cursor styling

Currently, when no guicursor value is provided (styling is disabled), we use some default values: block, ver25, or hor25 based on mode.

The TUI does not behave the same way, it uses block mode for all cases when guicursor is empty.

This change removes the cursor defaults, and applies block mode to all cases where guicursor is empty.

@jgehrig
Copy link
Collaborator Author

jgehrig commented May 1, 2023

I have some slight hesitancy on check-in for this fix, some users could complain of the exact opposite.

However, the TUI behaves as called out in the bug, so perhaps this will not be an issue?

@jgehrig jgehrig force-pushed the jg-1063-default-guicursor branch from 92108a5 to 4a911fa Compare May 3, 2023 01:05
Currently, when no guicursor value is provided (styling is disabled), we
use some default values: block, ver25, or hor25 based on mode.

The TUI does not behave the same way, it uses block mode for all cases
when guicursor is empty.

This change removes the cursor defaults, and applies block mode to all
cases where guicursor is empty.
@justinmk
Copy link
Contributor

justinmk commented Jun 14, 2023

The TUI does not behave the same way, it uses block mode for all cases when guicursor is empty.

I think that also matches Vim. If the OS provides an API for "cursor style preferences", that would be ideal. Otherwise, yes, if the user explicitly unsets 'guicursor' they are asking for "do as little as possible".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants